Systems and methods for dynamic device programming

ABSTRACT

Systems and methods for dynamic device programming in accordance with embodiments of the invention are disclosed. One embodiment includes a vehicle telematics device including a processor, a memory containing a dynamic telematics messaging application, a plurality of accumulators, and a communications interface, wherein the dynamic telematics messaging application directs the processor to obtain a first message data describing a requested set of sensor data using the communications interface, dynamically reconfigure the plurality of accumulators to measure the requested set of sensor data, and transmit a second message data describing the measured set of sensor data.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation of and claims priority under35 U.S.C. § 120 to U.S. patent application Ser. No. 15/828,102, entitled“SYSTEMS AND METHODS DYNAMIC DEVICE PROGRAMMING” by Zywicki, now U.S.Pat. No. 11,206,171, which was filed on Nov. 30, 2017, and which claimspriority to U.S. Provisional Patent Application No. 62/582,181, field onNov. 7, 20271, the entirety of each of which is expressly incorporatedherein by reference.

FIELD OF THE DISCLOSURE

The present invention relates to system communication processing andmore specifically to dynamically processing disparate messages.

BACKGROUND

Telematics is the integrated use of telecommunications and informatics.Telematics units are installed in vehicles to provide a variety oftelematics functionality in the vehicle. This functionality includes,but is not limited to, emergency warning systems, navigationfunctionality, safety warnings, vehicle location determination, andautomated driving assistance. Telematics units are also capable ofrecording data related to the operation of the vehicle and providingthat information for analysis, whether in real-time or during a timewhen the vehicle is being serviced. This information can be used in avariety of applications, such as fleet tracking, shipment tracking,insurance calculations, and in vehicle management and service.

SUMMARY

Systems and methods for dynamic device programming in accordance withembodiments of the invention are disclosed. One embodiment includes avehicle telematics device including a processor, a memory containing adynamic telematics messaging application, a plurality of accumulators,and a communications interface, wherein the dynamic telematics messagingapplication directs the processor to obtain a first message datadescribing a requested set of sensor data using the communicationsinterface, dynamically reconfigure the plurality of accumulators tomeasure the requested set of sensor data, and transmit a second messagedata describing the measured set of sensor data.

In another embodiment, the processor includes a plurality of processingengines.

In a further embodiment, at least one of the plurality of processingengines is a virtual processing engine.

In still another embodiment, a first processing engine in the pluralityof processing engines is directed to transcode the first message datainto a format usable by a second processing engine in the plurality ofprocessing engines.

In a still further embodiment, the first message data is encoded in astandardized message format.

In yet another embodiment, the vehicle telematics device is connected toa vehicle using the communications interface.

In a yet further embodiment, the communications interface includes adiagnostic port connector.

in another additional embodiment, the dynamic telematics messagingapplication further directs the processor to determine what sensordevices are available from the vehicle, generate configuration databased on the available sensor devices, and dynamically reconfigure theplurality of accumulators based on the configuration data.

In a further additional embodiment, dynamically reconfiguring theplurality of accumulators includes assigning at least one accumulator inthe plurality of accumulators to a sensor device.

In another embodiment again, the configuration data describes whatsensor devices are available and which sensor data are to be stored.

In a further embodiment again, a method for dynamically configuring avehicle telematics device includes obtaining a first message data from avehicle telematics server system using a communications interface,reconfiguring at least one accumulator in a plurality of accumulators tostore sensor data based on the first message data, and transmitting asecond message data describing the sensor data using the communicationsinterface.

In still yet another embodiment, the method further includes transcodingthe first message data from a first format to a second format, where thefirst format is not usable by at least one processing engine.

In a still yet further embodiment, the at least one processing engine isa virtual processing engine.

In still another additional embodiment, the method further includesconnecting to a vehicle via a communications interface, determining aplurality of sensor devices from the vehicle, generating a configurationdata based on the plurality of sensor devices, and reconfiguring the atleast one accumulator in the plurality of accumulators to store a set ofsensor data from the plurality of sensor devices.

In a still further additional embodiment, the configuration dataincludes priority data describing which sensor data should be measured.

In still another embodiment again, reconfiguring at least oneaccumulator in a plurality of accumulators to store sensor data furtherincludes updating a configuration data describing which sensor devicesare available, wherein the configuration data includes a priority datadescribing which sensor data should be measured.

In a still further embodiment again, the priority data includes abehavior profile.

In yet another additional embodiment, the first message data is obtainedfrom a dynamic telematics server system.

In a yet further additional embodiment, a vehicle telematics deviceincludes E first processing engine for directed to generate statusreports, a second processing engine directed to process sensor data, athird processing engine directed to transcode message data for the firstand second processing engines, a plurality of accumulators configured tostore sensor data, and a memory comprising a dynamic telematicsmessaging application, wherein the dynamic telematics messagingapplication directs the processor to obtain a first message data in afirst message format from a dynamic telematics server system, classifythe transcoded message data, transcode the first message data to asecond format using the third processing engine, process the transcodedmessage data using the appropriate processing engine, reconfigure theplurality of accumulators based on the transcoded message data, generatea second message data based on the sensor data stored by the pluralityof accumulators, and provide the second message data.

In yet another embodiment again, the first, second, and third processingengines are virtual processing engines.

In a yet further embodiment again, the vehicle telematics device furtherincludes a communications interface connected to the diagnostic port ofa vehicle.

In another additional embodiment again, the dynamic telematics messagingapplication further directs the processor to obtain sensor data from thevehicle.

Other objects, advantages and novel features, and further scope ofapplicability of the present invention will be set forth in part in thedetailed description to follow, and in part will become apparent tothose skilled in the art upon examination of the following, or may belearned by practice of the invention. The objects and advantages of theinvention may be realized and attained by means of the instrumentalitiesand combinations particularly pointed out in the prepended claims.

BRIEF DESCRIPTION

The description will be more fully understood with reference to thefollowing figures, which are presented as exemplary embodiments of theinvention and should not be construed as a complete recitation of thescope of the invention, wherein:

FIG. 1 is a conceptual illustration of a vehicle telematics system inaccordance with an embodiment of the invention;

FIG. 2A is a conceptual illustration of a vehicle telematics device inaccordance with an embodiment of the invention;

FIG. 2B is a conceptual illustration of a telematics server system inaccordance with an embodiment of the invention;

FIG. 3 is a flow chart illustrating a process for automaticallyconfiguring a vehicle telematics device in accordance with an embodimentof the invention;

FIG. 4 is a flow chart illustrating a process for reconfiguring vehicletelematics devices in accordance with an embodiment of the invention;and

FIG. 5 is a flow chart illustrating a process for transcoding messagedata in accordance with an embodiment of the invention.

DETAILED DESCRIPTION

Turning now to the drawings, systems and methods for dynamic deviceprogramming in accordance with embodiments of the invention aredisclosed. Fleets of vehicles are a core component of many industriessuch as logistics and personal transportation. In many cases, it can bebeneficial to be able to monitor and track the status of vehicles withinthe fleet. As such, many vehicles are equipped with vehicle telematicsdevices. These vehicle telematics devices can obtain and/or measure avariety of data regarding the conditions and/or location of the vehiclealong with receiving and transmitting data to telematics server systems.Vehicle telematics devices can have a set of accumulators configured tostore measured data. However, there are often not enough accumulators tostore all measurable data. Furthermore, vehicle telematics devices maybe preprogrammed to measure a certain set of data, but without knowingwhat type of vehicle it is going to be connected to, there is a chancethat accumulator space may be unused and/or the device itself may needto be reprogrammed post-installation. Vehicle telematics devices caninclude one or more processing engines. In a variety of embodiments,processing engines can include engines for processing and generatingstatus reports and processing and generating sensor data messages,although any processing engines can be utilized as appropriate to therequirements of specific applications of embodiments of the invention.

In many embodiments, vehicle telematics devices can automatically detectthe type of available data after connecting to a vehicle. In numerousembodiments, vehicle telematics devices can dynamically assignaccumulators to change what data is measured and/or reported back to atelematics server system. Vehicle telematics devices can change theirbehavior in response to messages from telematics server systemsincluding, but not limited to, what data is being stored, what data isbeing transmitted, the format of transmitted messages, and/or any otherbehavioral change as appropriate to the requirements of a givenapplication. In numerous embodiments, vehicle telematics devices includea processing engine for transcoding messages into formats usable byother processing engines. In this way, vehicle telematics devices canautomatically maintain compatibility with a variety of telematics serversystems and/or messaging formats while maintaining functionality and/orcompatibility with legacy on-board processing engines. Systems andmethods for dynamic telematics messaging, including a variety of formatsfor transmitting messages within a vehicle telematics system, that canbe utilized in accordance with embodiments of the invention aredescribed in U.S. patent application Ser. No. 15/818,260 entitled“Systems and Methods for Dynamic Telematics Messaging”, filed Nov. 20,2017, the disclosure of which is hereby incorporated by reference in itsentirety.

Vehicle Telematics Systems

Vehicle telematics systems in accordance with embodiments of theinvention can transmit a variety of data between a telematics serversystem and a vehicle telematics device. A conceptual diagram of avehicle telematics system in accordance with an embodiment of theinvention is shown in FIG. 1. The vehicle telematics system 10 includesa vehicle telematics device 20 that can communicate with a vehicle databus 22, an input/output (I/O) interface 24, and/or a network 30 asappropriate to the requirements of specific applications of embodimentsof the invention. In a variety of embodiments, vehicle telematics device20 communicates with a telematics server system 40 via the network 30.In a variety of embodiments, the network 30 is the Internet. In manyembodiments, the network 30 is any wired or wireless network, such as acellular network, between the vehicle telematics device 20 and thetelematics server system 40. In a number of embodiments, the telematicsserver system 40 implemented using a single server system. In severalembodiments, the telematics server system 40 is implemented usingmultiple server systems.

In a variety of embodiments, the vehicle telematics device 20 isinstalled in a vehicle having a vehicle data bus 22. In severalembodiments, the vehicle telematics device 20 is connected to a vehiclediagnostic connector that provides access to the vehicle data bus 22.The vehicle telematics device 20 can obtain data from any of a varietyof vehicle devices connected to the vehicle data bus 22 utilizing any ofa variety of techniques as appropriate to the requirements of specificapplications of embodiments of the invention. Vehicle devices caninclude, but are not limited to, engine sensors, electronic control unit(ECU) devices, alternator sensors, vibration sensors, voltage sensors,oxygen sensors, Global Positioning System (GPS) receivers, ignitiondevices, weight sensors, wireless network devices, and/or accelerationdetermination devices. Systems and methods for connecting to a vehicledata bus that can be utilized in accordance with embodiments of theinvention are described in SAE J1978, titled “OBD II Scan Tool,” firstpublished by SAE International of Troy, Mich. on Mar. 1, 1992 and lastupdated Apr. 30, 2002. Systems and methods for obtaining data fromdevices connected to a vehicle data bus are described in SAE J1979,titled “E/E Diagnostic Test Modes,” first published by SAE Internationalon Dec. 1, 1991 and last updated Aug. 11, 2014. The disclosures of SAEJ1978 and SAE J1979 are hereby incorporated by reference in theirentirety.

The vehicle telematics device 20 can include any of a variety of sensorsand/or devices, including those described above with respect to thevehicle data bus and any described in more detail below, to obtain dataregarding the status of the vehicle. The vehicle telematics device 20can also communicate with any of a variety of sensors and/or devicesusing the I/O interface 24. The I/O interface 24 can be any connection,including wired and wireless connections, as appropriate to therequirements of specific applications of embodiments of the invention.In several embodiments, the vehicle telematics device 20 is capable ofexecuting scripts to read data and/or perform particular processes.These scripts can be pre-loaded on the device and/or obtained from thetelematics server system 40, vehicle data bus 22, and/or the I/Ointerface 24 as appropriate to the requirements of specific applicationsof embodiments of the invention. The vehicle telematics device 20 can beself-powered and/or connected into the electrical system of the vehiclein which the vehicle telematics device 20 is installed. In a variety ofembodiments, the vehicle telematics device is powered via the vehicledata bus 22 and/or the I/O interface 24. In many embodiments, thevehicle telematics device 20 utilizes a Global Positioning System (GPS)receiver in order to determine the location, speed, and/or accelerationof the vehicle. However, it should be noted that anylocation-determining techniques, such as cellular tower triangulation,wireless network geolocation techniques, and dead reckoning techniques,could be utilized as appropriate to the requirements of specificapplications of embodiments of the invention.

In a variety of embodiments, the vehicle telematics device 20 and/ortelematics server system 40 provides a user interface allowing forvisualizing and interacting with the data transmitted and/or receivedbetween the systems. In several embodiments, the vehicle telematicsdevice 20 and/or telematics server system 40 provide an interface, suchas an application programming interface (API) or web service thatprovides some or all of the data to third-party systems for furtherprocessing. Access to the interface can be open and/or secured using anyof a variety of techniques, such as by using client authorization keys,as appropriate to the requirements of specific applications of theinvention.

Although a specific architecture of a vehicle telematics system inaccordance with embodiments of the invention are discussed above andillustrated in FIG. 1, a variety of architectures, including sensors andother devices and techniques not specifically described above, can beutilized in accordance with embodiments of the invention. Furthermore,the processes described herein can be performed using any combinationthe vehicle telematics device and/or the telematics server system asappropriate to the requirements of specific applications of embodimentsof the invention.

Vehicle Telematics Devices

Vehicle telematics devices in accordance with many embodiments of theinvention can transmit and receive data. A conceptual illustration of avehicle telematics device in accordance with an embodiment of theinvention is shown in FIG. 2A. The vehicle telematics device 200includes a processor 210 in communication with a memory 240. Processor210 can include any number of processing engines. In many embodiments,three processing engines are used. Processing engines can havespecialized purposes including, but not limited to, processing sensordata, generating reports, transcoding messages, and/or any other purposeas appropriate to the requirements of a given application. Processingengines can be implemented in hardware and/or as virtual processingengines. In many embodiments, memory includes a series of accumulatorsconfigured to store bit strings. Accumulators can be assigned staticidentifiers, e.g. 0, 1, 2 . . . etc. The vehicle telematics device 200includes a communications interface 220 capable of sending and receivingdata. Although the processor 210 and communications interface 220 areillustrated as separate components, some or all of these devices can beimplemented using a single-chip solution as appropriate to therequirements of specific applications of embodiments of the invention.

Sensor devices 230 can include, but are not limited to, RPM sensors,voltage sensors, GPS receivers, noise sensors, vibration sensors,acceleration sensors, weight sensors, and any other device capable ofmeasuring data regarding a vehicle as appropriate to the requirements ofspecific applications of embodiments of the invention. In certainembodiments, sensor devices 230 are included within the vehicletelematics device 200. However, vehicle telematics devices can alsoacquire sensor data from sensor devices located externally to thevehicle telematics device 200. In a variety of embodiments, sensordevices 230 include any sensors integrated into the vehicle andtransmitted to the vehicle telematics device 200. In many embodiments,sensors are integrated into the vehicle and transmitted over a vehicledata bus. In numerous embodiments, sensor readings are stored as bitstrings in the series of accumulators.

In several embodiments, the memory 240 is any form of storage storing avariety of data, including, but not limited to, a messaging application242, device configuration data 244, and/or sensor data 246. In manyembodiments, the messaging application 242, device configuration data244, and/or sensor data 246 are stored using an external server systemand received by the vehicle telematics device 200 using thecommunications interface 220. Device configuration data can be used todirect the processor to generate messages in a chosen static messageprofile. In a variety of embodiments, dynamic messaging applications cangenerate dynamic messages that require minimal processing by dynamictelematics messaging systems. In numerous embodiments, deviceconfiguration data 244 describes what sensor data is available and/orwhich types of sensor data are currently being collected.

Turning now to FIG. 2B, a conceptual illustration of a telematics serversystem is shown. The telematics server system 260 contains a processor270 in communication with a memory 290 and a communications interface280. Processor 270 can be any type of computational processing unit,including, but not limited to, microprocessors, central processingunits, graphical processing units, parallel processing engines, or anyother type of processor as appropriate to the requirements of a givenapplication. The communications interface 280 can be utilized totransmit and receive messages from and to vehicle telematics devices, aswell as to transmit data between server systems and interface devices.Communications interface 280 can include multiple ports and/ortechnologies in order to communicate with various devices as appropriateto the requirements of specific applications of embodiments of theinvention.

Memory 290 can be implemented using any combination of volatile and/ornon-volatile memory, including, but not limited to, random accessmemory, read-only memory, hard disk drives, solid-state drives, flashmemory, or any other memory format as appropriate to the requirements ofa given application. In several embodiments, the memory 290 stores avariety of data, including, but not limited to, a dynamic messagingapplication 292 and/or received report data 293. In many embodiments,the dynamic messaging application 292 and/or received report data 293are stored using an external server system and received by thetelematics server system 200 using the communications interface 280.

Processor 210 and processor 270 can be directed, by messagingapplication 242 and dynamic messaging application 292, to perform avariety of dynamic telematics messaging processes. As described in moredetail below dynamic messaging processes can include, but are notlimited to, dynamically configuring a vehicle telematics device andgenerating message data including data read using one or more sensordevices.

Although specific architectures for vehicle telematics devices andtelematics server systems in accordance with embodiments of theinvention are conceptually illustrated in FIGS. 2A and 2B, any of avariety of architectures, including those that store data orapplications on disk or some other form of storage and are loaded intomemory at runtime, can also be utilized. In a variety of embodiments, amemory includes circuitry such as, but not limited to, memory cellsconstructed using transistors, that are configured to storeinstructions. Similarly, a processor can include logic gates formed fromtransistors (or any other device) that dynamically perform actions basedon the instructions stored in the memory. In several embodiments, theinstructions are embodied in a configuration of logic gates within theprocessor to implement and/or perform actions described by theinstructions. In this way, the systems and methods described herein canbe performed utilizing both general-purpose computing hardware and bysingle-purpose devices such as, but not limited to, systems-on-a-chip(SoC). Furthermore, telematics server systems can be implemented onmultiple servers within at least one server system. For example,telematics server system systems can be implemented on various remote“cloud” server systems as appropriate to the requirements of a givenapplication.

Configuring Vehicle Telematics Devices

When vehicle telematics devices are connected to vehicles, they candetermined what data and/or is available, and accumulators can beassigned to different data types. Dynamic telematics messaging processesin accordance with embodiments of the invention can include querying thevehicle to generate initialization data and automatically configure thevehicle telematics device. Turning now to FIG. 3, a process fordynamically configuring a vehicle telematics device in accordance withan embodiment of the invention is illustrated. Process 300 includesconnecting (310) to a vehicle. In many embodiments, the connection ismade to the vehicle data bus. In numerous embodiments, the connection tothe vehicle data bus is made via a diagnostic port located within thevehicle. However, any number of connection methods, including directwiring into particular devices and/or sensors located within thevehicle, can be used as appropriate to the requirements of a givenapplication.

Process 300 further includes determining (320) available sensor devices.In numerous embodiments, the determination of available sensor devicesincludes detecting what sensor devices are available via the vehicledata bus. In many embodiments, the available sensors devices isdetermined using a bus discovery process, such as those described in SAEJ1978 and J1979 incorporated by reference above. The bus discoveryprocess can provide a list of sensor devices in a variety of formats,including a bit string matching a standardized format, as appropriate tothe requirements of specific applications of embodiments of theinvention. In a variety of embodiments, vehicle identificationinformation such as, but not limited to, a vehicle identification number(VIN), are used to determine what sensor devices are available. Innumerous embodiments, vehicle identification information can be used toquery a database to determine an appropriate initial deviceconfiguration data.

The vehicle telematics device can be dynamically configured (330). Inmany embodiments, device configuration data generated based on theavailable sensor devices is used to configure the vehicle telematicsdevice. In numerous embodiments, sensor data are dynamically assigned toaccumulators. If there are more sensor devices and/or collectable typesof data available than there are accumulators, a record can be kept ofavailable sensor devices. In many embodiments, which sensors areassigned to accumulators is determined based on a predetermined prioritydata describing which data is of highest value. In a number ofembodiments, the assignment of sensor devices to accumulators can beautomatically updated based on requests for data from particular sensordevices.

In a number of embodiments, process 300 also includes initializing (340)data collection and/or providing (350) a vehicle report. In manyembodiments, initializing data collection includes storing sensor datain accumulators. Vehicle reports can include information about availablesensor data, the type of vehicle, the time of install, and/or any otherinitialization information as appropriate to the requirements of a givenapplication. In several embodiments, the vehicle report is generated bya script that automatically compiles the current value of one or moreaccumulators.

Specific processes for configuring vehicle telematics devices inaccordance with embodiments of the invention are described above andshown with respect to FIG. 3; however, any number of processes,including those that use alternative techniques for determiningavailable sensor devices and/or storing sensor data, can be utilized asappropriate to the requirements of a specific application in accordancewith embodiments of the invention.

Dynamically Reconfiguring Vehicle Telematics Devices

There are situations where data that is accessible by a vehicletelematics device is not being recorded and/or there is a request forparticular data to be measured by a vehicle telematics device. Inseveral embodiments, messages can be provided to vehicle telematicsdevices to dynamically reconfigure its behavior. Dynamic telematicsmessaging processes in accordance with embodiments of the invention caninclude dynamically reconfiguring vehicle telematics devices in responseto a message. Turning now to FIG. 4, a method for dynamicallyreconfiguring a vehicle telematics device in accordance with anembodiment of the invention is illustrated. Process 400 includesobtaining (410) message data. The message type can be determined (420).Message types can be, but are not limited to, messages that requestchanges in sensor data, message format, communications protocol,firmware updates, and/or any other reconfigurable behavior in accordancewith an embodiment of the invention.

The vehicle telematics device can be dynamically reconfigured (430)based on the message data. In many embodiments, when the message dataincludes a request for a change in sensor data, the requested sensordata is assigned to an accumulator. The particular accumulator utilizedcan be determined automatically and/or defined in the message data asappropriate to the requirements of specific applications of embodimentsof the invention. If there are no available accumulators, an accumulatorcurrently in use can be reassigned to store the requested sensor data.In numerous embodiments, the message indicates which sensor data is nolonger required so that the accumulator previously used to store thedata is reassigned. In a variety of embodiments, the accumulator to bereassigned is based on predetermined priority data. However, whichaccumulator is reassigned can be determined in any number of ways,including, but not limited to number of times an accumulator has beenreassigned, and/or any other metric as appropriate to the requirementsof a given application of the invention. In a variety of embodiments,device configuration data can describe a number of behavior profilesindicating accumulator assignments. In many embodiments, the messagedata can include a request for a new behavior profile from storedbehavior profiles and/or transmit a new behavior profile. When themessage requests a change in reporting data format(s), the vehicletelematics device can dynamically reconfigure the message structure usedto generate vehicle reports. In numerous embodiments, when the messagerequests a change in transmission protocol, the vehicle telematicsdevice can be dynamically reconfigured to communicate via the updatedtransmission protocol.

Process 400 can further include providing (440) requested data. Innumerous embodiments, the requested data contains the newly requestedsensor data. In many embodiments, the requested data is in a messageformat includes containers for a large number of different types ofdata, but only the types of data stored accumulators are stored in themessage. In numerous embodiments, identifying data about the vehicleand/or vehicle telematics device are stored in the message. Identifyingdata can be stored as metadata in message format. In a variety ofembodiments, the requested data includes one or more vehicle reports asdescribed in more detail above.

Specific processes for dynamically reconfiguring vehicle telematicsdevices in accordance with embodiments of the invention are describedabove and shown with respect to FIG. 4; however, any number ofprocesses, including those that use alternative techniques forallocating memory, can be utilized as appropriate to the requirements ofa specific application in accordance with embodiments of the invention.

Transcoding Message Data

Vehicle telematics devices can perform a variety of processes totranscode message data in a first format into a second format usable byspecific processing engines. Dynamic telematics messaging processes inaccordance with embodiments of the invention can include transcodingreceived messages into specific formats. For example, the first messageformat can utilize the extensible markup language (XML) standard, whilethe second format includes a hex-encoded bit string. However, it shouldbe noted that any data formats can be utilized and/or transcoded asappropriate to the requirements of specific applications of embodimentsof the invention.

Turning now to FIG. 5, a process for providing transcoded message datain accordance with an embodiment of the invention is illustrated.Process 500 includes obtaining (510) message data. In numerousembodiments, obtained message data is in a format that is typically notreadable by vehicle telematics devices. Message data can be transcoded(520) into a usable format. In many embodiments, message data is encodedin a standardized format that is not readable by vehicle telematicsdevices. Standardized message data can be converted into a devicespecific format. In numerous embodiments, message data is transcoded byapplying a set of rules describing transformations of instruction datastored within message data. In many embodiments, the instruction dataprovides requests for data such as, but not limited to, sensor data. Ina variety of embodiments, instruction data describes changes tocommunications protocols. The instruction data can be stored astranscoded message data. The transcoded message data can be provided(530). In numerous embodiments, the transcoded message data is providedto hardware within a vehicle telematics device. In a variety ofembodiments, the transcoded message data is provided to a processingengine executing within the vehicle telematics device. However, anytranscoded message data can be provided to any number of devices suchas, but not limited to, relays, modems, user interfaces, and/or anyother device as appropriate to the requirements of a given application.

In many embodiments, transcoded message data can trigger processes fordynamically reconfiguring vehicle telematics devices. In numerousembodiments, data requested by transcoded message data can be provided(540). In numerous embodiments, the provided data includes one or morevehicle reports as described in more detail above.

Specific processes for providing transcoded message data in accordancewith embodiments of the invention are described above and shown withrespect to FIG. 5; however, any number of processes, including thosethat use alternative transcoding techniques, can be utilized asappropriate to the requirements of a specific application in accordancewith embodiments of the invention.

Although the present invention has been described in certain specificaspects, many additional modifications and variations would be apparentto those skilled in the art. In particular, any of the various processesdescribed above can be performed in alternative sequences and/or inparallel in order to achieve similar results in a manner that is moreappropriate to the requirements of a specific application. It istherefore to be understood that the present invention can be practicedotherwise than specifically described without departing from the scopeand spirit of the present invention. Thus, embodiments of the presentinvention should be considered in all respects as illustrative and notrestrictive. It will be evident to the person skilled in the art tofreely combine several or all of the embodiments discussed here asdeemed suitable for a specific application of the invention. Throughoutthis disclosure, terms like “advantageous”, “exemplary” or “preferred”indicate elements or dimensions which are particularly suitable (but notessential) to the invention or an embodiment thereof, and may bemodified wherever deemed suitable by the skilled person, except whereexpressly required. Accordingly, the scope of the invention should bedetermined not by the embodiments illustrated, but by the appendedclaims and their equivalents.

1. A vehicle telematics device comprising: one or more processors; a setof accumulators configured to store sensor data; and one or more memoryhaving stored therein a plurality of instructions that, in response toexecution by the one or more processors, cause the vehicle telematicsdevice to: assign each accumulator of the set of accumulators to storecorresponding sensor data based on a predetermined priority of thecorresponding sensor data; receive message data that identifiesrequested sensor data; select a first accumulator from the set ofaccumulators to be reassigned from storing the sensor data previouslyassigned to the first accumulator to storing the requested sensor data;and reassign the first accumulator from storing the sensor datapreviously assigned to the first accumulator to storing the requestedsensor data.
 2. The vehicle telematics device of claim 1, wherein toselect the first accumulator comprises to select the first accumulatorbased on the predetermined priority of the sensor data previouslyassigned to the first accumulator.
 3. The vehicle telematics device ofclaim 1, wherein to select the first accumulator comprises to: determinewhether an accumulator of the set of accumulators is available to storethe requested sensor data; and in response to a determination that theaccumulator of the set of accumulators is not available to store therequested sensor data, select the first accumulator from the set ofaccumulators to be reassigned from storing the sensor data previouslyassigned to the first accumulator to storing the requested sensor data.4. The vehicle telematics device of claim 1, wherein the message dataalso identifies a desired accumulator of the set of accumulators tostore the requested sensor data, and wherein the plurality ofinstructions, in response to execution by the one or more processors,further cause the vehicle telematics device to: determine whether thedesired accumulator of the set of accumulators is available to store therequested data, wherein to select the first accumulator comprises toselect the desired accumulator in response to a determination that thedesired accumulator is available to store the requested data.
 5. Thevehicle telematics device of claim 4, wherein to select the firstaccumulator comprises to select, in response to a determination that thedesired accumulator is not available to store the requested data, afirst accumulator, different from the desired accumulator, from the setof accumulators based on the sensor data previously assigned to thefirst accumulator.
 6. The vehicle telematics device of claim 1, whereinthe message data further identifies sensor data that is no longerrequired, and wherein to select the first accumulator comprises toselect a first accumulator from the set of accumulators that waspreviously assigned to store the sensor data that is no longer required.7. The vehicle telematics device of claim 1, wherein to select the firstaccumulator comprises to select the first accumulator based on dataindicative of a number of times the first accumulator has beenpreviously reassigned from storing first sensor data to storing secondsensor data different from the first sensor data.
 8. The vehicletelematics device of claim 7, wherein to select the first accumulatorcomprises to update, in response to selecting the first accumulator, thedata indicative of the number of times the first accumulator has beenpreviously reassigned.
 9. The vehicle telematics device of claim 1,wherein the one or more memory further has stored therein a set ofbehavior profiles, wherein each behavior profile of the set of behaviorprofiles identifies an assignment of each accumulator of the set ofaccumulators to store corresponding sensor data, wherein to assign eachaccumulator comprises to assign each accumulator of the set ofaccumulators based on a first behavior profile of the set of behaviorprofiles, wherein the message data further identifies a second behaviorprofile of the set of behavior profiles different from the firstbehavior profile, and wherein to select the first accumulator comprisesto select the first accumulator from the set of accumulators based onthe second behavior profile.
 10. A method for configuring a vehicletelematics device, the method comprising: assigning each accumulator ofa set of accumulators of the vehicle telematics device to storecorresponding sensor data based on a predetermined priority of thecorresponding sensor data; receiving message data that identifiesrequested sensor data; selecting a first accumulator from the set ofaccumulators to be reassigned from storing the sensor data previouslyassigned to the first accumulator to storing the requested sensor data;and reassigning the first accumulator from storing the sensor datapreviously assigned to the first accumulator to storing the requestedsensor data.
 11. The method of claim 10, wherein selecting the firstaccumulator comprises selecting the first accumulator based on thepredetermined priority of the sensor data previously assigned to thefirst accumulator.
 12. The method of claim 10, wherein selecting thefirst accumulator comprises: determining whether an accumulator of theset of accumulators is available to store the requested sensor data; andin response to a determination that the accumulator of the set ofaccumulators is not available to store the requested sensor data,selecting the first accumulator from the set of accumulators to bereassigned from storing the sensor data previously assigned to the firstaccumulator to storing the requested sensor data.
 13. The method ofclaim 10, wherein the message data also identifies a desired accumulatorof the set of accumulators to store the requested sensor data, andwherein the method further comprises determining whether the desiredaccumulator of the set of accumulators is available to store therequested data, wherein selecting the first accumulator comprisesselecting the desired accumulator in response to a determination thatthe desired accumulator is available to store the requested data. 14.The method of claim 10, wherein the message data further identifiessensor data that is no longer required, and wherein selecting the firstaccumulator comprises selecting a first accumulator from the set ofaccumulators that was previously assigned to store the sensor data thatis no longer required.
 15. The method of claim 10, wherein selecting thefirst accumulator comprises selecting the first accumulator based ondata indicative of a number of times the first accumulator has beenpreviously reassigned from storing first sensor data to storing secondsensor data different from the first sensor data.
 16. The method ofclaim 10, wherein assigning each accumulator comprises to assigning eachaccumulator of the set of accumulators based on a first behavior profileof a set of behavior profiles stored on the vehicle telematics device,wherein each behavior profile of the set of behavior profiles identifiesan assignment of each accumulator of the set of accumulators to storecorresponding sensor data, wherein the message data further identifies asecond behavior profile of the set of behavior profiles different fromthe first behavior profile, and wherein selecting the first accumulatorcomprises selecting the first accumulator from the set of accumulatorsbased on the second behavior profile.
 17. One or more non-transitory,machine-readable media having a plurality of instructions stored thereonthat, when executed, cause a vehicle telematics device to: assign eachaccumulator of a set of accumulators of the vehicle telematics device tostore corresponding sensor data based on a predetermined priority of thecorresponding sensor data; receive message data that identifiesrequested sensor data; select a first accumulator from the set ofaccumulators to be reassigned from storing the sensor data previouslyassigned to the first accumulator to storing the requested sensor data;and reassign the first accumulator from storing the sensor datapreviously assigned to the first accumulator to storing the requestedsensor data.
 18. The one or more non-transitory, machine-readable mediaof claim 17, wherein to select the first accumulator comprises to selectthe first accumulator based on the predetermined priority of the sensordata previously assigned to the first accumulator.
 19. The one or morenon-transitory, machine-readable media of claim 17, wherein the messagedata further identifies sensor data that is no longer required, andwherein to select the first accumulator comprises to select a firstaccumulator from the set of accumulators that was previously assigned tostore the sensor data that is no longer required.
 20. The one or morenon-transitory, machine-readable media of claim 17, wherein to selectthe first accumulator comprises to select the first accumulator based ondata indicative of a number of times the first accumulator has beenpreviously reassigned from storing first sensor data to storing secondsensor data different from the first sensor data.